CW2-37 404 Page #20
Merged
CW2-37 404 Page #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…exactly the same component at ./resources
…page in index.tsx
derekxu04
approved these changes
Jul 12, 2024
frontend/src/pages/404.tsx
Outdated
| </p> | ||
| <motion.div className="opacity-0" whileHover={{ opacity: 1 }} transition={{duration: 0.2}}> | ||
| <p className="text-2xl pt-10"> | ||
| While we may have found some tomfoolery, we haven't found your page :'( |
There was a problem hiding this comment.
Haha I like the animation
I'm wondering if you can do this just with tailwind, don't have to use framer, could potentially be easier and more inline with the rest of the css
Also: I think it would be cool to have some CS themed error messages, maybe even alternate between a few random ones, could be a fun easter egg (e.g. just asking chatgpt lol:
- Oops! This page must have been garbage collected.
- Looks like this page hit a segmentation fault.
- 404 Error: The page you’re looking for has been deprecated.
etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why the changes are required?
To add a 404 page
Changes
Screenshots
Comments
Nothing much. Once the website is live, I believe should migrate to next.js 14 if we are to continue developing the website. We are currently using the /pages directory as well as the "outdated 404" method - and also can't take advantage of the website's endpoints (which I assume is why we are creating a separate backend for some reason). This is just something I'd like to bring to attention, nothing but isn't urgent at any capacity however.